3.4 Configuring SMS and email notifications

You can choose whether to allow SMS, email, or both types of notification when sending provisioning messages to mobile devices.

You can also choose whether to display OTP codes on-screen or to send them to the mobile using SMS.

To allow provisioning messages:

  1. From the Configuration category, select the Operation Settings workflow.

  2. On the Devices tab, set the following options:

    • Mobile Provision Via Email – set this option to allow the notifications of mobile IDs to be sent to the user's email address.

    • Mobile Provision Via SMS – set this option to allow the notifications of mobile IDs to be sent to the user's mobile phone number.

    Note: You can select one or both of these options. If you select both options, you can select which method to use when you request the mobile identity.

  3. On the Notifications tab, set the following options:

    • Send Mobile OTP via SMS – set this option to allow the operator to send the OTP authentication code directly to the mobile device.

      Note: If you set Send Mobile OTP via SMS to Yes, as a security feature, the OTP is sent as an SMS while the notification message must be sent using email and not SMS; make sure you select the Mobile Provision Via Email option on the Devices tab.

    • Mail Format – make sure this option is set to HTML.

  4. Click Save changes.

3.4.1 Configuring the SMS gateway

You can configure the system to use any SMS gateway. You must customize the following file:

customSMS.asp

Versions of this file are installed to the MyID web server in the following locations:

Where <edition> is WebPIV for PIV, and WebENT for non-PIV editions of MyID.

You must make the same changes in each version of the file. If you have created any custom translations of the MyID web site, you must also make the same change in the custom versions.

The sample file installed with the system is set up to use the SMS gateway provided by www.2sms.com – if you are using this service, edit the username line to include your 2sms account, and the password line to include your 2sms password.

If you are using any other system, you must customize the ASP file to conform to the calling requirements of your own SMS gateway.

This ASP file implements the following function:

customSendSMS(message, mobileNumber, userRS)

where:

The function returns the response from the SMS gateway.

You can implement your system in any way. You are required only to send the body contained in message to the phone number in mobileNumber, and return the response from the gateway.

Note: You must keep a backup of this file once you have customized it.

3.4.2 Configuring SMS and email certificate renewal notifications

You can decide whether to send renewal messages through email, through SMS, or through both email and SMS.

To allow MyID to send SMS messages, set the SMS email notifications on the General tab of the Operation Settings workflow to Yes.

By default, SMS messages are sent to an Email to SMS gateway, in the format <cellnumber>@<gateway>, where:

For example: [email protected]

If this is not suitable, you can customize the sp_CustomPrepareSMS stored procedure in the MyID database.

You can use different content for email and SMS certificate renewal messages, and different content for different kinds of device – mobile or card, for example. Six additional renewal messages are provided – three messages for SMS to mobile devices, and three messages for email to mobile devices. Use the Email Templates workflow to edit the content of these messages.

Note: If you have upgraded your MyID system, MyID does not update your stored procedure to prevent the overwriting of your changes. The base stored procedure has been updated, and you must edit the sp_CustomPrepareSMS stored procedure to allow it to work. If your stored procedure contains the following:

-- Output an XML string
@xml NVARCHAR(MAX) OUT

change it to:

-- Output an XML string
@xml NVARCHAR(4000) OUT